New-MailboxRestoreRequest never finishes. I have to set it as a high priority to get it to even start, but after it starts, it just hangs.

Here is the command I ran to do the RestoreRequest from a recoveryDB to a target user folder

New-MailboxRestoreRequest -SourceDatabase RecoveryDB1 -SourceStoreMailbox "test exchange" -TargetMailbox "Exchange Recovery" -TargetRootFolder "ExTestRecovered" -AllowLegacyDNMismatch -SkipMerging StorageProviderForSource -Priority Emergency

The -SkipMerging StorageProviderFor switch is recommended in the release notes, and fails without it.

http://technet.microsoft.com/en-us/library/jj150489(v=exchg.150).aspx

Doing a Get-MailboxRestoreRequest shows me "InProgress", but when viewing the statistics, the StatusDetail shows Relinquished, with no good indication as to why.

Get-MailboxRestoreRequest |Get-MailboxRestoreRequestStatistics

Name                                   StatusDetail              TargetAlias                           PercentComplete
----                                   ------------              -----------                           ---------------
MailboxRestore                         Relinquished              ExchangeRecovery                      0


Get-MailboxRestoreRequest |Get-MailboxRestoreRequestStatistics |fl


RunspaceId                             : 4075ae17-fc61-4001-9440-faa61258d8e8
Name                                   : MailboxRestore
Status                                 : InProgress
StatusDetail                           : Relinquished
SyncStage                              : None
Flags                                  : IntraOrg, Pull, HighPriority
RequestStyle                           : IntraOrg
Direction                              : Pull
Protect                                : False
Priority                               : Emergency
WorkloadType                           : Local
Suspend                                : False
SourceExchangeGuid                     : 7da64e4d-eb04-4c3c-b0db-e34b5c90338c
SourceRootFolder                       :
SourceVersion                          : Version 15.0 (Build 620.0)
SourceDatabase                         : RecoveryDB1
SourceServer                           : server.domain.dc
MailboxRestoreFlags                    : Recovery
TargetAlias                            : ExchangeRecovery
TargetIsArchive                        : False
TargetExchangeGuid                     : fe6cb236-ae43-4ae5-a582-c12ad6596c6f
TargetRootFolder                       : ExTestRecovered
TargetVersion                          : Version 15.0 (Build 620.0)
TargetDatabase                         : MailboxDB
TargetServer                           : server.domain.dc
TargetMailboxIdentity                  : domain.dc/Support/Domain/Exchange Recovery
IncludeFolders                         : {}
ExcludeFolders                         : {}
ExcludeDumpster                        : False
ConflictResolutionOption               : KeepSourceItem
AssociatedMessagesCopyOption           : Copy
BatchName                              :
BadItemLimit                           : 0
BadItemsEncountered                    : 0
LargeItemLimit                         : 0
LargeItemsEncountered                  : 0
QueuedTimestamp                        : 4/24/2013 9:05:42 AM
StartTimestamp                         :
LastUpdateTimestamp                    : 4/24/2013 9:37:46 AM
CompletionTimestamp                    :
SuspendedTimestamp                     :
OverallDuration                        : 00:40:02
TotalSuspendedDuration                 :
TotalFailedDuration                    :
TotalQueuedDuration                    : 00:00:01
TotalInProgressDuration                : 00:00:07
TotalStalledDueToCIDuration            :
TotalStalledDueToHADuration            :
TotalStalledDueToMailboxLockedDuration :
TotalStalledDueToReadThrottle          :
TotalStalledDueToWriteThrottle         :
TotalStalledDueToReadCpu               :
TotalStalledDueToWriteCpu              :
TotalStalledDueToReadUnknown           :
TotalStalledDueToWriteUnknown          :
TotalTransientFailureDuration          :
TotalIdleDuration                      : 00:00:07
MRSServerName                          :
EstimatedTransferSize                  : 0 B (0 bytes)
EstimatedTransferItemCount             : 0
BytesTransferred                       : 0 B (0 bytes)
BytesTransferredPerMinute              :
ItemsTransferred                       : 0
PercentComplete                        : 0
CompletedRequestAgeLimit               : 30.00:00:00
PositionInQueue                        :
InternalFlags                          : SkipStorageProviderForSource
FailureCode                            :
FailureType                            :
FailureSide                            :
Message                                : Informational: The request has been temporarily postponed: The request has
                                         been relinquished. --> Resource reservation has expired.
FailureTimestamp                       :
IsValid                                : True
ValidationMessage                      :
OrganizationId                         :
RequestGuid                            : b4f4e829-f15f-42ea-9b8e-183230dbf1e1
RequestQueue                           : MailboxDB
Identity                               : RequestGuid (b4f4e829-f15f-42ea-9b8e-183230dbf1e1), RequestQueue:
                                         (69d8b142-10d5-4f28-a6bd-581a4ad0978e)
Report                                 :
ObjectState                            : New

Some additional info. I have removed the restore requests, and tried again. Doing a Get-MailboxRestoreRequest shows 1 request in the Queue. However doing a Get-mailboxRestoreRequest | Get-MailboxRestoreRequestStatistics | fl, shows it is 2/2 in a Queue, which looks like it makes it so it will never change to "inProgress". 

[PS] C:\Windows\system32>Get-MailboxRestoreRequest

Name                                           TargetMailbox                                  Status
----                                           -------------                                  ------
MailboxRestore                                 domain.dc/Support/TEP/Exchange Recovery           Queued


[PS] C:\Windows\system32>

PositionInQueue                        : 2/2 (Position/Queue L

Scott, were you able to get restore request going ?

Ive got a single mailboxrestorerequest with status "In Progress", but the StatusDetail shows Relinquished with Message "Informational: The request has been temporarily postponed: The request has been relinquished. --> Resource reservation has expired."

Hello Scott,

I have exactly the same behaviour. Do you get that worked?

Please run these cmdlets and send us the output, it appears move requests are throttled

could you tell us the CPU and memory configuratino on your mailbox and CAS servers ?

run get-mailboxdatabasecopystatus on the mailbox server and check the status of Content indexing 

- get-exchangediagnosticinfo

- get-exchangediagnosticinfo -process msexchangemailboxreplication

- in the event logs look for any errors or warnings for mailbox replciation service

-Manju

I have the exact same problem with a restore. can't find a way around it, any other idea ?

Same issue here.  I've also noticed that mounting the Recovery Database shows successful in the event log but the get-mailboxdatabase still shows mounted (and mounted on server) status as blank.  subsequent mount-database all show successful even if I run it three times in a row.

Also, the first time I successfully launched new-mailboxdatabaserestorerequest, it failed just others mentioned here.  I removed the request and created another one and this one is just sitting in the queue indefinitely.

Edit: I did just see some warnings in the event log:

The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: RDB1
Error: MapiExceptionRecoveryMDBMismatch: Unable to open message store. (hr=0x80004005, ec=1165)

lol, to add more to the weirdness, I tried to log on to my mailbox via OWA but it connected me to the Recovery Database mailbox.  I didn't realize it until I saw that when I was sending messages to myself, and I wasn't receiving them.  I checked the MTA queue and saw messages associated with the recovery database.  I logged out of OWA and removed the recovery database.  I logged back in to OWA and it connected me to the regular database where things worked fine.

Same behavior for me. In the eventvwr i've got this error too:

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: 'e0e30246-6d52-424c-99d2-aa1328cc12d9'
Database GUID: '0520d356-8e39-406c-92a4-aa957cacf18b'
Error: Resource reservation failed for 'MdbWrite(TMP01)' (MdbLatency(TMP01)): load ratio -1, load state 'Unknown', metric (null)..

I guess MS doesn't reply to threads in the forums anymore.  I haven't seen a reply from MS since June 18 on this.

Anyway, I also noticed that mounting a database via the command-line doesn't actually even show that the database is mounted.  I did a check on all of my databases and I see that all of them have blanks next to the Mounted status if I do a get-mailboxdatabase.  The web admin shows that they are mounted but that doesn't help with recovery databases since they don't appear in the web admin.

So I'm happy to say that I see the solution for this.  It is to install CU2 which was just release a few days ago.  Once I did that, everything worked as it normally should.  You don't need any special -SkipMerging StorageProviderForSource anymore and that is even taken out of the notes.  All of the weird behavior went away when I updated to CU2.

I must say though that I pity anyone that is currently using CU1 (or possibly lower) and actually has a database crash.  Unfortunately, none of this is even included in the notes for CU2 (actually, almost no bug fix notes are currently available) and it really should be a high-priority for everyone to move to this or to test your current backup/restore solution.